DXL init error

I see the following error

The init script has been run.
-R-E- DXL: <Line:1> null IPC parameter was passed into argument position 1
Backtrace:
    <wizard/welcome/welcomewiz.dxl:703>
    <Line:1>
-I- DXL: execution halted

 

code snippet is

evalTop_ "initDXLServer server 5093"
print "The init script has been run.\n"

Can anyone shed some light as to what the issue is? Thanks!!


 

 


praveen_k573 - Thu Jun 05 15:07:29 EDT 2014

Re: DXL init error
Mathias Mamsch - Fri Jun 06 03:58:16 EDT 2014

To me it seems, that the IPC server (int) perm returns null, so you would need to check if and why that command fails. It could be that the port is already blocked by another DXL Server running on the same port. Or that a firewall blocks that port. To be sure you should do something like this:

evalTop_ "
IPC socket = server 5093
if (null socket) error \"Socket could not be opened on that port!\"
initDXLServer socket
"

However I find it curious that the error traceback includes the welcomewiz.dxl ... Did you actually include that code in the welcome wizard?

Another thing you need to know is, that evalTop_ will run the code only AFTER your DXL has completed. That is the reason, why you first see the output of the print statement and afterwards the error.

Maybe that helps, regards, Mathias

Re: DXL init error
llandale - Fri Jun 06 17:00:30 EDT 2014

Mathias Mamsch - Fri Jun 06 03:58:16 EDT 2014

To me it seems, that the IPC server (int) perm returns null, so you would need to check if and why that command fails. It could be that the port is already blocked by another DXL Server running on the same port. Or that a firewall blocks that port. To be sure you should do something like this:

evalTop_ "
IPC socket = server 5093
if (null socket) error \"Socket could not be opened on that port!\"
initDXLServer socket
"

However I find it curious that the error traceback includes the welcomewiz.dxl ... Did you actually include that code in the welcome wizard?

Another thing you need to know is, that evalTop_ will run the code only AFTER your DXL has completed. That is the reason, why you first see the output of the print statement and afterwards the error.

Maybe that helps, regards, Mathias

I think "completed" BTW includes code at the end of a dialog callback, and also when you "show" a dialog.  That is, there is no more code to run at the moment even when the dialog is open.   "Modal" dialogs are not "completed", such as when you "infoBox" or "block" a dialog.

-Louie